Exploring Requirements 2 by Gerald M. Weinberg

Author:Gerald M. Weinberg
Language: eng
Format: epub
Tags: design, designing, software, software testing, requirements, software development, ambiguity, software quality, product development, product planning, specifications
Publisher: Gerald M. Weinberg

19.2 Using the Metric as a Test

One useful model of design says design is the process of removing ambiguity. In terms of this model, design proceeds through a series of steps: creating an approximate design, testing for ambiguity, removing the ambiguity found, and retesting the new approximation. Eventually, the tests say the latest approximation is close enough, and design stops.

19.2.1 Measuring three kinds of ambiguity

In this view, everything done from recognition of a problem to final disposition can be considered design, including the unconscious, implicit design assumptions as well as the conscious, explicit design decisions. As an oversimplification, we can think of three major kinds of ambiguity we must measure and remove, each associated with a major part of the total design activity.

1. Problem-statement ambiguity, as we know, is ambiguity in the problem statement, or requirements (see Figure 19-1).

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.